Steps needed once to reconfigure settings (background info)

1. Re-run: bash resources.sh init-project --project $GCS_PROJECT --bucket $GCS_BUCKET_NAME --ip-range $IP_RANGE --ms-path <path>/monitor.sh to generate new workflow_options.json & cromwell.conf

2. New workflow_options.json should contain a new line for the monitoring script

3. Run: bash start.sh $GCS_INSTANCE_NAME --server-account $GCS_SERVICE_ACCOUNT --project $GCS_PROJECT --boot-disk-size=50GB --boot-disk-type=pd-standard --machine-type=e2-standard-2 to create a VM

4. Within the VM, check that /shared/cromwell/workflow_options.json reflects the new change

If user provides a path to a monitoring script, every task will generate a monitoring log file

NOTE: if specified, it is the user responsibility to ensure that the monitoring script is in $BUCKET/$MS_PATH, otherwise it breaks

Tasks

• script works and produces monitoring.log for every task
  |__ - works but breaks estimate-bills script

Tasks beyond the scope of this pull request:

• pull these monitoring scripts from cloud to local
• create a summary
  Analysis of Monitoring Scripts #30